Flex Programmer User Manual

Flex Programmer is used to load Flex programming files, program a supported Sprintek USB HID device, and verify the programmed contents.

Start the App

1. Extract the Flex Programmer package.
2. Run flexprogrammer.exe on Windows, or flexprogrammer on Linux or macOS.
3. Connect one supported Sprintek FlexMatrix device by USB.

The device selector at the top of the window shows the connected device. If more than one supported device is connected, select the target device before programming.

Load Files

Select Load Files... or press F4.

Flex Programmer accepts these file types:

• *_code.flex
• *_setting.flex
• *_livesetting.flex

Raw *_setting.bin and *_livesetting.bin files may be loaded for workflows that explicitly use raw setting payloads. Raw AppCode .bin files are not accepted as normal programming input; AppCode must be loaded from a signed *_code.flex package.

When loading a release upgrade folder, select the Flex files supplied with the release. The app can also auto-fill matching companion files that share the same base name.

After loading, the file rows show checksums and package hash information. If a signed package is invalid, encrypted AppCode cannot be decrypted, or a file does not match the expected format, the app reports the failure in the output panel.

Program and Verify

1. Confirm the correct device is selected.
2. Confirm the intended Code, Setting, and Live Setting files are loaded.
3. Select Program & Verify or press F5.
4. Wait for the output panel to show the final pass or fail result.

Do not disconnect the device while programming is running.

By default, Flex Programmer may skip AppCode programming when the loaded AppCode package matches the AppCode already on the selected device. It checks the device AppCode container and AppCode region checksum before entering boot update mode. Settings and live settings can still be programmed when AppCode programming is skipped.

Verify Only

Select Verify or press F6 to compare loaded files against the selected device without programming new data.

Read IC

Select Read IC... or press F7 to read supported device data to files. Readback files are saved as:

• <base>_code_readback.bin
• <base>_setting.bin
• <base>_livesetting.bin
• <base>_summary_sha256.txt

The AppCode readback file includes the readable container header and AppCode header. Bytes in the unreadable AppCode gap between them are filled with 0xFF, and the polled AppCode checksum is appended at the end.

Auto Program

Enable Auto Program or press F10 for single-device workflows where programming should start automatically when a supported device is connected and files are already loaded.

Use Auto Program only when the workstation process controls which device is connected.

Program AppCode Always

Program AppCode Always is unchecked by default. When unchecked, Flex Programmer can skip AppCode programming if the loaded AppCode package already matches the selected device.

Enable Program AppCode Always from the Commands menu, toolbar, or Preferences when AppCode should be programmed every time even if the package appears to match the device. The shortcut key is F11.

Output and Logs

The output panel shows file loading, signature verification, programming, verify, and error messages for the current session.

Flex Programmer also writes:

• programmer.log
• program-records.jsonl

The log folder is named logs and is saved beside the Flex Programmer executable.

The exact log and program record paths are printed at the start of each Flex Programmer session.

These logs may include operator, host, machine, device, package hash, checksum, timestamp, and pass/fail information. Review logs before sharing them outside your organization.

Troubleshooting

• No matching HID devices: confirm the device is connected, powered, and supported by this Flex Programmer release.
• Select device: more than one supported device is connected. Choose the intended device in the device selector.
• File load failed: confirm the selected files came from the correct release upgrade folder and were not renamed or modified.
• Signature or package failure: use a package generated by the approved Sprintek release process.
• Verify failed: confirm the loaded files match the intended device firmware and settings.

More Help

Use Help > Use Limitation for software use restrictions and Help > About for the installed Flex Programmer version.